home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19951130-19960209
/
000108_news@columbia.edu_Thu Dec 14 15:12:31 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA05548
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun>); Fri, 15 Dec 1995 10:15:36 -0500
Received: (from news@localhost) by apakabar.cc.columbia.edu (8.6.12/8.6.12) id KAA16788 for kermit.misc@watsun; Fri, 15 Dec 1995 10:15:32 -0500
Path: news.columbia.edu!sol.ctr.columbia.edu!news.uoregon.edu!news.u.washington.edu!news.alt.net!news.serv.net!solaris.cc.vt.edu!hookup!jussieu.fr!fdn.fr!r2d2.fdn.org!uunet!in2.uu.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Error: Can't arp resolve
Message-Id: <1995Dec14.211231.69704@cc.usu.edu>
Date: 14 Dec 95 21:12:31 MDT
References: <4ap9b9$10oo@useneta1.news.prodigy.com>
Distribution: world
Organization: Utah State University
Lines: 24
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <4ap9b9$10oo@useneta1.news.prodigy.com>, SWHN62A@prodigy.com (Joseph Beasley iii) writes:
> I am trying to connect a dos machine to a linux box via ethernet. I have
> the packet drivers installed, but I get a message, "can't arp resolve the
> address". I can connect fine in windows using trumpet, but using the
> latest version of PC Kermit gives this error message.
-----------
There are a couple of things which might cause this: Linux itself
and a bug in the MSK code if both network adapters are from the same vendor
(for gosh sakes). Some versions of Linux (I don't run it so please don't
ask me which versions etc) have broken ARP code. Much trouble over it.
The MSK bug is an addition to deal with NDIS drivers which echo
packets being sent. Yes, that's right. To detect and discard them I compare
source MAC address with the machine's own MAC address and discard if they
match. Alas, the quick-compare code (it sees every incoming packet so it
must be really fast) stepped through three rather than six bytes of MAC
address by mistake, and the first three Ethernet bytes are the vendor code.
I meant well, I really did, scout's honor. It's not patchable I'm sorry to
say.
If you will contact me personally, jrd@cc.usu.edu, let's see if we
can sort out the problem. Test question #1, while I grade final exams here,
is can you converse with a non-Linux machine? If so then that's a step in
the right direction. Extra credit is what happens if you change board vendor
in either machine.
Joe D.